Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add/skip pricing page when connecting from editor blocks #39865

Merged

Conversation

CodeyGuyDylan
Copy link
Contributor

@CodeyGuyDylan CodeyGuyDylan commented Oct 22, 2024

Proposed changes:

  • Add skipPricingPage prop to the useConnection hook that passes the skip_pricing param to the connection page
  • In the connect banner on editor components, go directly to connect page instead of redirecting to My Jetpack. This allows the user to connect and get back to what they were doing as quickly as possible

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

P2: pbNhbs-bQ3-p2

Does this pull request change what data or activity we track or use?

No

Testing instructions:

  1. Checkout this branch via the Jetpack Beta plugin or your local dev environment
  2. Connect your site but not your user account
  3. Go to wp-admin/post-new.php to create a new post
  4. Add any block that requires user connection (AI Assistant, for example)
    image
  5. Click on the Connection CTA, ensure you are sent to the main connection screen at https://wordpress.com/jetpack/connect/authorize
  6. Ensure that the skip_pricing query parameter exists in the URL
  7. Approve the connection or log-in if necessary
  8. Ensure you are redirected back to the same post you were editing
    image

Copy link
Contributor

github-actions bot commented Oct 22, 2024

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the add/skip-pricing-page-when-connecting-from-editor-blocks branch.

    • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.
  • To test on Simple, run the following command on your sandbox:

    bin/jetpack-downloader test jetpack add/skip-pricing-page-when-connecting-from-editor-blocks
    
    bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/skip-pricing-page-when-connecting-from-editor-blocks
    

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

Copy link
Contributor

github-actions bot commented Oct 22, 2024

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Choose a review path based on your changes:
    • A. Team Review: add the "[Status] Needs Team Review" label
      • For most changes, including minor cross-team impacts.
      • Example: Updating a team-specific component or a small change to a shared library.
    • B. Crew Review: add the "[Status] Needs Review" label
      • For significant changes to core functionality.
      • Example: Major updates to a shared library or complex features.
    • C. Both: Start with Team, then request Crew
      • For complex changes or when you need extra confidence.
      • Example: Refactor affecting multiple systems.
  3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!


Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

  • WordPress.com Simple releases happen semi-continuously (PCYsg-Jjm-p2).
  • WoA releases happen weekly.
  • Releases to self-hosted sites happen monthly. The next release is scheduled for November 5, 2024 (scheduled code freeze on November 4, 2024).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

@github-actions github-actions bot added [Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you! [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ labels Oct 22, 2024
@CodeyGuyDylan CodeyGuyDylan force-pushed the add/skip-pricing-page-when-connecting-from-editor-blocks branch from 73accdc to 6dcbdf2 Compare October 23, 2024 16:05
logo?: React.ReactNode;
}

const ConnectionScreenBody: FC< ConnectScreenProps > = props => {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There were more changes on this page on a previous iteration, however this is still a typing improvement, so I think we can keep it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should handle that at some point tho, since keeping two different types is not very maintainable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, I was thinking during the TypeScript refactor project 😄

@CodeyGuyDylan CodeyGuyDylan added [Status] Needs Team Review and removed [Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you! labels Oct 23, 2024
IanRamosC
IanRamosC previously approved these changes Oct 25, 2024
Copy link
Contributor

@IanRamosC IanRamosC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some nitpicks, but the functionality tests well.

autoTrigger: false,
skipPricingPage: true,
} );
const { autosave } = useAutosaveAndRedirect();
const { tracks } = useAnalytics();

const goToCheckoutPage = ( event: MouseEvent< HTMLButtonElement > ) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor nitpick: I know the name of the prop is goToCheckoutPage, but that's misleading in this scenario (especially after this change 😅 ). I think we could update at least the name of the method here.

// The redirection is handled this way to ensure we get the right redirectUri
// In the case that the post is new and unsaved, the component requires a re-render
// in order to get the correct URI when the handler is called.
if ( isRedirecting ) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another nitpick, this variable name could be something like isReadyToRedirect or something like that. To me, calling an action (handleConnectuser) when isRedirecting is true makes me think that it'll interrupt the redirect and do the other thing instead.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice workaround, btw 😅

@CodeyGuyDylan CodeyGuyDylan force-pushed the add/skip-pricing-page-when-connecting-from-editor-blocks branch from 5e40bbc to b33d9c7 Compare October 29, 2024 15:33
Copy link
Contributor

@IanRamosC IanRamosC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! :shipit:

@CodeyGuyDylan CodeyGuyDylan merged commit 890e73b into trunk Oct 29, 2024
73 checks passed
@CodeyGuyDylan CodeyGuyDylan deleted the add/skip-pricing-page-when-connecting-from-editor-blocks branch October 29, 2024 18:23
@github-actions github-actions bot added this to the jetpack/14.0 milestone Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[JS Package] Connection [Package] My Jetpack [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ RNA
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants